Active antenna element (aae) implementation for facilitating 6lowpan data access

ABSTRACT

A scheme for providing access to 6LoWPAN data in a wireless access network comprising a Digital Unit (DU) coupled to one or more Radio Units (RU) via CPRI links, each RU in turn coupled to one or more radio dot (RD) elements via Ethernet cable links. In one embodiment, an RD element includes a cable front-end interfaced with the Ethernet cable link, a radio front-end interfaced between the cable front-end and an antenna or a suitable access point. A sensor component may be included that is configured to generate sensor data with respect to a measurement variable, which sensor data may be packaged in a 6LoWPAN data format for transmission to the RU element coupled to the RD element.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application discloses subject matter that is related to the subjectmatter of the following U.S. patent application(s): (i) “SYSTEMS,METHODS, APPARATUSES, DEVICES AND ASSOCIATED COMPUTER-READABLE MEDIA FORPROVIDING 6LOWPAN DATA ACCESS” (Ericsson Ref. No.: P42124-US1),application Ser. No. ______, filed Feb. 21, 2014, in the name(s) ofSamita Chakrabarti, John Larkins, Jaume Rius Riu, John Fornehed andChenguang Lu; (ii) “BASEBAND UNIT (BBU) IMPLEMENTATION FOR FACILITATING6LOWPAN DATA ACCESS” (Ericsson Ref. No.: P42566-US1), application Ser.No. ______, filed Feb. 21, 2014, in the name(s) of Samita Chakrabarti,John Larkins, Jaume Rius Riu, John Fornehed and Chenguang Lu; and (iii)“PICO-RRU-BASED NETWORK IMPLEMENTATION FOR FACILITATING 6LOWPAN DATAACCESS” (Ericsson Ref. No.: P42568-US1), application Ser. No. ______,filed Feb. 21, 2014, in the name(s) of Samita Chakrabarti, John Larkins,Jaume Rius Riu, John Fornehed and Chenguang Lu; each of which is herebyincorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to communication networks. Moreparticularly, and not by way of any limitation, the present disclosureis directed to providing or otherwise facilitating access with respectto information in Internet Protocol (IP) version 6 (IPv6) over Low PowerWireless Personal Area Network (6LoWPAN) format in a network.

BACKGROUND

6LoWPAN is an acronym of “Internet Protocol (IP) version 6 (IPv6) overLow Power Wireless Personal Area Networks” that defines a technologystandardized in IEEE 802.15.4 where IPv6 packets may be sent andreceived in a network involving low-power radio devices. Such devicesare typically constrained with respect to memory/processing resources,power consumption, and radio transmission range. Integration of anetwork of 6LoWPAN-compliant low-power devices, which may be usuallydeployed in indoor applications, with an external IP network, be it IPv4or IPv6, remains a challenge and continues to present a significantobstacle to implementing advanced IPv6-based services, especially inInternet of Things (IoT) or Internet of Everything (IoE) architectures.

SUMMARY

The present patent application discloses systems, methods, devices,apparatuses and associated computer-readable media having executableprogram instructions thereon for providing or otherwise facilitating6LoWPAN data access in a number of implementations. In one aspect, anembodiment of a method operating at a Radio Unit (RU) element of anaccess system is disclosed for facilitating access with respect toinformation in 6LoWPAN format. The claimed embodiment comprisesreceiving 6LoWPAN data (“6LO data”) packets from a router coupled to anexternal packet-switched network; examining a destination IP address ofthe 6LO data packets and determining an address of at least one radiodot (RD) element to which the 6LO data packets are to be delivered;repackaging the 6LO data packets as a control channel message in aformat specified for a control channel associated with a communicationlink using Ethernet cabling (e.g., CAT 5/6/7 cabling; hereinafterreferred to as an Ethernet cable link or Ethernet cable communicationlink) between the RU element and the at least one RD element; andtransmitting the repackaged 6LO data packets to the at least one RDelement via the Ethernet cabling communication link as the controlchannel message.

In another embodiment, a system is disclosed for providing access withrespect to information in 6LoWPAN format. The claimed embodimentcomprises a Digital Unit (DU) element having baseband functionality thatis configured to interface with a cellular radio communications networkadapted for mobile telephony and data (for example, including but notlimited to 2G/3G/4G/5G or Next Generation networks; hereinafter referredto as a cellular radio communications network); an RU element coupled tothe DU element using a first connection and to at least one RD elementusing a second connection, the RU element having an interface forreceiving 6LO data packets from a router coupled to an externalpacket-switched network; a bridging function module included in the RUelement and configured to: examine a destination IP address of the 6LOdata packets and determine an address of the at least one RD element towhich the 6LO data packets are to be delivered; and repackage the 6LOdata packets as a control channel message in a format specified for acontrol channel associated with the second connection. A transceivermodule is included in the RU element for transmitting the repackaged 6LOdata packets to the at least one RD element via the second connection asthe control channel message.

In another embodiment, a non-transitory computer-readable medium isdisclosed containing instructions stored thereon which, when executed bya processor of an RU element, facilitate access with respect toinformation in 6LoWPAN. The claimed embodiment comprises a code portionfor processing 6LO data packets received from a router coupled to anexternal packet-switched network; a code portion for examining adestination IP address of the 6LO data packets and for determining anaddress of at least one RD element to which the 6LO data packets are tobe delivered, wherein the at least one RD element is coupled to the RUunit via an Ethernet cable communication link (i.e., a communicationlink using Ethernet CAT 5/6/7 cabling); a code portion for repackagingthe 6LO data packets as a control channel message in a format specifiedfor a control channel associated with the Ethernet cable communicationlink between the RU and the at least one RD elements; and a code portionfor facilitating transmission of the repackaged 6LO data packets to theat least one RD element via the Ethernet communication link as thecontrol channel message.

In another aspect, an embodiment of a method operating at a DU (i.e.,Baseband Unit or BBU) element of a wireless access system is disclosedfor providing access with respect to information in 6LoWPAN format. Theclaimed embodiment comprises receiving 6LO data packets from a routercoupled to an external packet-switched network; examining a destinationIP address of the 6LO data packets and determining an address of atleast one RD element to which the 6LO data packets are to be delivered;based on the address of the at least one RD element, determining anaddress of a corresponding RU element associated with the at least oneRD element; repackaging the 6LO data packets in a format specified for acontrol/management (C/M) channel associated with a communication linkdisposed between the DU and RU elements and operable with Common PublicRadio Interface (CPRI) protocol; and transmitting the repackaged 6LOdata packets to the RU element as a CPRI C/M message via thecommunication link operable with the CPRI protocol, wherein the CPRI C/Mmessage includes the address of the at least one RD element.

In a still further embodiment, a method operating at an RU element of anaccess system is disclosed for facilitating access with respect toinformation in 6LoWPAN format. The claimed embodiment comprisesreceiving 6LO data packets from a DU element coupled to an externalpacket-switched network, wherein the 6LO data packets are packaged in aC/M channel message associated with a communication link operable withthe CPRI protocol; unpacking the C/M message and obtaining a destinationaddress of an RD element to which the 6LO data packets are to bedelivered; repackaging the 6LO data packets as a control channel messagein a format specified for a control channel associated with an Ethernetcable communication link between the RU and RD elements; andtransmitting the repackaged 6LO data packets to the RD element via theEthernet cable communication link as the control channel message.

In a still further embodiment, a system is disclosed for providingaccess with respect to 6LoWPAN information. The claimed embodimentcomprises a DU element having baseband functionality that is configuredto interface with a cellular radio communications network, the DUelement including an interface for receiving 6LO data packets from arouter coupled to an external packet-switched network; a bridgingfunction module included in the DU element and configured to: examine adestination IP address of the 6LO data packets and determine an addressof at least one RD element to which the 6LO data packets are to bedelivered; determine, based on the address of the RD element, an addressof an RU element corresponding to the at least one RD element; andrepackage the 6LO data packets in a format specified for a C/M channelassociated with a communication link disposed between the DU element andthe corresponding RU element and operable with the CPRI protocol. The DUelement further includes a transceiver module for transmitting therepackaged 6LO data packets to the corresponding RU element as a CPRIC/M message via the communication link operable with the CPRI protocol,wherein the CPRI C/M message includes the address of the at least one RDelement.

In a still further embodiment, a non-transitory computer-readable mediumis disclosed containing instructions stored thereon which, when executedby a processor of a DU element, facilitate access with respect to6LoWPAN information. The claimed embodiment comprises a code portion forprocessing 6LoWPAN data packets received from a router coupled to anexternal packet-switched network; a code portion for examining adestination IP address of the 6LO data packets and for determining anaddress of at least one RD element to which the 6LO data packets are tobe delivered; a code portion, responsive to determining the address ofthe at least one RD element, for determining an address of acorresponding RU element associated with the at least one RD element; acode portion for repackaging the 6LO data packets in a format specifiedfor a C/M channel associated with a communication link disposed betweenthe DU element and the corresponding RU element and operable with theCPRI protocol; and a code portion for facilitating transmission of therepackaged 6LO data packets to the corresponding RU element as a CPRIC/M message via the communication link operable with the CPRI protocol,wherein CPRI C/M message includes the address of the at least one RDelement.

In yet another aspect, an active antenna element (AAE) or radio dot (RD)embodiment operable in a 6LoWPAN access system is disclosed. The claimedembodiment comprises a cable front-end (FE) block or module forinterfacing with an Ethernet cable communication link connecting to anRU element disposed in the access system; a radio FE block or modulecoupled to the cable FE block and an antenna operative to receive andtransmit radio signals for effectuating wireless communications withrespect to one or more user equipment (UE) devices; a sensor element orcomponent configured to generate sensor data with respect to ameasurement variable; a processor coupled to the sensor component and amodem interfacing with the cable FE block, the processor configured tofacilitate packaging of the sensor data as 6LoWPAN data packets; and acontrol channel repackager operative under control of the processor forrepackaging the 6LO data packets to be transmitted via the modem as acontrol channel message in a format specified for a control channelassociated with the Ethernet cable communication link between the RU andRD elements.

Another RD embodiment is disclosed that includes a cable front-end (FE)element for interfacing with an Ethernet cable communication linkconnecting to a Radio Unit (RU) element disposed in the access system; aradio FE block coupled to the cable FE block and an antenna operative toreceive and transmit radio signals for effectuating wirelesscommunications with respect to one or more UE devices; a sensor elementconfigured to generate sensor data with respect to an environmentalvariable as 6LoWPAN data packets; a processor coupled to the sensorcomponent and a modem interfacing with the cable FE block; and a controlchannel repackager operative under control of the processor forrepackaging the 6LO data packets to be transmitted via the modem as acontrol channel message in a format specified for a control channelassociated with the Ethernet cable communication link between the RU andRD elements.

Yet another RD embodiment is disclosed that includes a cable front-end(FE) element for interfacing with an Ethernet cable communication linkconnecting to an RU element disposed in the access system; a radio FEblock coupled to the cable FE block and an antenna operative to receiveand transmit radio signals for effectuating wireless communications withrespect to one or more UE devices; an access point (AP) elementconfigured to facilitate transmission and reception of 6LoWPAN datapackets wirelessly with respect to one or more 6LoWPAN-compliantdevices; a processor coupled to the AP element and a modem interfacingwith the cable FE block; and a control channel repackager operativeunder control of the processor for repackaging the 6LO data packetsreceived via the AP element to be transmitted via the modem as a controlchannel message in a format specified for a control channel associatedwith the Ethernet cable communication link between the RU and RDelements.

In a still further embodiment, a method operating at an RD element isdisclosed for facilitating access with respect to 6LoWPAN information.The claimed embodiment comprises obtaining source data; determining ifthe source data is compliant with the 6LoWPAN format; and if so,repackaging the 6LoWPAN-compliant source data to be transmitted as acontrol channel message in a format specified for a control channelassociated with an Ethernet cabling link between the RD and acorresponding RU element coupled thereto and disposed in the accesssystem.

In a still further embodiment, a non-transitory computer-readable mediumis disclosed containing instructions stored thereon which, when executedby a processor of an RD element configured to operate in an accesssystem, facilitate providing access with respect to 6LoWPAN information.The claimed embodiment comprises a code portion for processing sourcedata; a code portion for determining if the source data is compliantwith the 6LoWPAN format; and a code portion, responsive to determiningthat the source data is compliant with the 6LoWPAN format, forrepackaging the 6LoWPAN-compliant source data to be transmitted as acontrol channel message in a format specified for a control channelassociated with an Ethernet cable link between the RD and acorresponding RU element coupled thereto and disposed in the accesssystem.

In a still further aspect, an embodiment of a method operating in aPico-Radio Remote Unit (PRRU)-based access system (PRAS) is disclosedfor providing access with respect to 6LoWPAN information. The claimedembodiment comprises receiving, at a Baseband Unit (BBU) element (whichmay be somewhat equivalent to an embodiment of a DU element describedhereinabove), 6LoWPAN data packets from a router coupled to an externalpacket-switched network; examining a destination IP address of the 6LOdata packets and determining an address of at least one pico remoteradio unit (PRRU) element to which the 6LO data packets are to bedelivered; based on the address of the at least one PRRU element,determining an address of a remote radio hub (RHUB) elementcorresponding to the at least one PRRU element; repackaging the 6LO datapackets in a format specified for a C/M channel associated with a firstcommunication link disposed between the BBU and RHUB elements andoperable with the CPRI protocol; transmitting the repackaged 6LO datapackets to the RHUB element in a first CPRI C/M message via the firstcommunication link operable with CPRI protocol, the CPRI C/M messageincluding the address of the PRRU element; unpacking, at the RHUBelement, the first CPRI C/M message received from the BBU element andobtaining the at least one PRRU element's address to which the 6LO datapackets are to be delivered; and repackaging the 6LO data packets in asecond CPRI C/M message and transmitting the second CPRI C/M message tothe at least one PRRU element via a second communication link operablewith the CPRI protocol. It should be appreciated that in a PRASarchitecture, the BBU may be equivalently implemented as a DU element inother embodiments described above.

In another embodiment, a system is disclosed for providing access withrespect to 6LoWPAN information in a PRRU network. The claimed embodimentcomprises a BBU element having baseband functionality that is configuredto interface with a cellular radio communications network, the BBUelement including an interface for receiving 6LoWPAN data packets from arouter coupled to an external packet-switched network; a bridgingfunction module included in the BBU element and configured to: examine adestination IP address of the 6LO data packets and determine an addressof at least one PRRU element to which the 6LO data packets are to bedelivered; determine, based on the address of the PRRU element, anaddress of an RHUB element corresponding to the at least one PRRUelement; and repackage the 6LO data packets in a format specified for aC/M channel associated with a first communication link disposed betweenthe BBU element and the corresponding RHUB element and operable with theCPRI protocol. The BBU element further includes transceiver module fortransmitting the repackaged 6LO data packets to the corresponding RHUBelement as a first CPRI C/M message multiplexed with other CPRI data(e.g., ID data flows) via the first communication link, the first CPRIC/M message including the address of the at least one PRRU element. TheRHUB element is configured to unpack the first CPRI C/M message receivedfrom the BBU element and obtain the at least one PRRU element's addressto which the 6LO data packets are to be delivered; and repackage the 6LOdata packets in a second CPRI C/M message and transmit the second CPRIC/M message to the at least one PRRU element via a second communicationlink operable with the CPRI protocol.

In a still further embodiment, a non-transitory computer-readable mediumis disclosed containing instructions stored thereon which, when executedby a processor of a BBU element, facilitate access with respect to6LoWPAN information. The claimed embodiment comprises a code portion forprocessing 6LoWPAN data packets received from a router coupled to anexternal packet-switched network; a code portion for examining adestination IP address of the 6LO data packets and for determining anaddress of at least one PRRU element to which the 6LO data packets areto be delivered; a code portion, responsive to determining the addressof the at least one PRRU element, for determining an address of acorresponding RHUB element associated with the at least one PRRUelement; a code portion for repackaging the 6LO data packets in a formatspecified for a C/M channel associated with a first communication linkdisposed between the BBU element and the corresponding RHUB element andoperable with the CPRI protocol; and a code portion for facilitatingtransmission of the repackaged 6LO data packets to the correspondingRHUB element as a CPRI C/M message via the first communication linkoperable with the CPRI protocol, wherein the CPRI C/M message includesthe address of the at least one PRRU element.

In still further embodiments, a gateway/router is disclosed that may becoupled to a DU element or an RU element of a wireless access system(e.g., a radio dot system or RDS) embodiment described above. Being abordering node between an external IP network and the RDS, thegateway/router may be referred to as an RGR node. In one variation, theRGR node comprises, inter alia, a transceiver module for coupling to anInternet Protocol (IP) version 6 (IPv6) network; and a transceivermodule for coupling to a DU element disposed in an indoor wirelessaccess network (e.g., RDS) configured to transport information in6LoWPAN format, wherein the DU element is interfaced with a cellularcore network and coupled to a plurality of RU elements via a set ofrespective first connections. Each RU element is, in turn, coupled to acorresponding plurality of 6LoWPAN endpoints via a set of respectivesecond connections. An adaptation layer module configured to supportfragmentation and reassembly operations for information between IPv6format and 6LoWPAN format is included in the RGR node. A Point-to-Point(P2P) connection database operatively coupled to the adaptation layermodule maintains data identifying a plurality of P2P connections withrespect to the plurality of 6LoWPAN endpoints, wherein a P2P connectionis defined by an address combination including at least an address ofthe DU element, an address of a particular RU element and an address ofa particular 6LoWPAN endpoint coupled to the particular RU element. Oneor more processors of the RGR node are coupled to a memory andconfigured to control the adaptation layer module and facilitatedownlink (DL) transmission of IPv6 information received from the IPv6network to a 6LoWPAN endpoint via the DU element and a corresponding RUelement and uplink (UL) transmission of 6LoWPAN information receivedfrom a 6LoWPAN endpoint via a corresponding RU element and the DUelement to a next hop in the IPv6 network responsive to correspondingP2P connections identified in the P2P connection database. In a relatedvariation, the RGR node may be coupled to an RU element of the RDSnetwork, wherein the IP bridging functionality resides. The overallfunctionality of such an RGR node is similar to the RGR node coupled toa DU element as described above, mutatis mutandis.

In still further aspects, additional embodiments of non-transitorycomputer-readable media containing instructions stored thereon aredisclosed for performing one or more embodiments of the methods setforth hereinbelow when executed by corresponding hardware platforms.

Advantages of the present invention include, but not limited to,leveraging an indoor wireless solution for facilitating access to 6LOdata in an architecture without having to deploy a separate network. AsInternet of Things (IoT) or Internet of Everything (IoE) architecturescontinue to evolve and IPv6 backhaul infrastructure becomes morepervasive, embodiments of the present disclosure provide advantageoussolutions for capitalizing on such advances, which can incentivizeservice providers/operators to provision new and additionalIoT/IoE-based services. Further, by integrating sensor capabilitieswithin the access network's downstream endpoints, the need for adedicated sensor network (e.g., a capillary network) can be obviated.Additional benefits and advantages of the embodiments will be apparentin view of the following description and accompanying Figures.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present disclosure are illustrated by way of example,and not by way of limitation, in the Figures of the accompanyingdrawings in which like references indicate similar elements. It shouldbe noted that different references to “an” or “one” embodiment in thisdisclosure are not necessarily to the same embodiment, and suchreferences may mean at least one. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

The accompanying drawings are incorporated into and form a part of thespecification to illustrate one or more exemplary embodiments of thepresent disclosure. Various advantages and features of the disclosurewill be understood from the following Detailed Description taken inconnection with the appended claims and with reference to the attacheddrawing Figures in which:

FIG. 1 depicts an example network environment including a 6LoWPAN dataaccess system (6LODAS) according to an embodiment of the present patentapplication;

FIG. 2 depicts an example network environment including a 6LODASaccording to another embodiment of the present patent application;

FIG. 3 depicts an example frequency band plan for use with an embodimentof a 6LODAS of the present patent application;

FIG. 4 depicts a block diagram of an active antenna element (AAE) or aradio dot (RD) having a sensor component according to an embodiment ofthe present patent application;

FIG. 5 depicts a block diagram of an AAE or RD having a 6LO access point(AP) according to an embodiment of the present patent application;

FIG. 6 depicts a block diagram of an AAE or RD having a 6LO AP accordingto another embodiment of the present patent application;

FIG. 7A depicts a block diagram of an embodiment of a gateway/borderrouter adapted to interoperate with a Digital Unit (DU), Baseband Unit(BBU) or a Radio Unit (RU) element for purposes of the present patentapplication;

FIGS. 7B and 7C depict block diagrams of an RU element and a DU element,respectively, according to an embodiment of the present patentapplication;

FIG. 8 depicts an example process flow illustrating data transferbetween a 6LODAS endpoint and associated gateway router usingpoint-to-point connectivity and encapsulation according to anembodiment;

FIG. 9 depicts a flowchart of blocks relative to various steps and/oracts that may take place at an RU element for effectuating data transferwith respect to the embodiment shown in FIG. 1;

FIG. 10 depicts a flowchart of blocks relative to various steps and/oracts that may take place at an RD element with respect to receiving6LoWPAN data from an RU element;

FIGS. 11A and 11B depict flowcharts of blocks relative to various stepsand/or acts that may take place at DU and RU elements for effectuatingdata transfer with respect to the embodiment shown in FIG. 2;

FIGS. 12A and 12B depicts flowchart of blocks relative to various stepsand/or acts that may take place for effectuating data transfer withrespect to one or more embodiments of the present patent application;

FIG. 13 depicts an example network environment including aPico-RRU-based access system (PRAS) for accessing 6LoWPAN data accordingto another embodiment of the present patent application; and

FIG. 14 depicts a flowchart of blocks relative to various steps and/oracts that may take place for effectuating data transfer with respect tothe embodiment shown in FIG. 13.

DETAILED DESCRIPTION OF THE DRAWINGS

In the following description, numerous specific details are set forthwith respect to one or more embodiments of the present patentdisclosure. However, it should be understood that one or moreembodiments may be practiced without such specific details. In otherinstances, well-known circuits, subsystems, components, structures andtechniques have not been shown in detail in order not to obscure theunderstanding of the example embodiments. Accordingly, it will beappreciated by one skilled in the art that the embodiments of thepresent disclosure may be practiced without such specificcomponents-based details. It should be further recognized that those ofordinary skill in the art, with the aid of the Detailed Description setforth herein and taking reference to the accompanying drawings, will beable to make and use one or more embodiments without undueexperimentation.

Additionally, terms such as “coupled” and “connected,” along with theirderivatives, may be used in the following description, claims, or both.It should be understood that these terms are not necessarily intended assynonyms for each other. “Coupled” may be used to indicate that two ormore elements, which may or may not be in direct physical or electricalcontact with each other, co-operate or interact with each other.“Connected” may be used to indicate the establishment of communication,i.e., a communicative relationship, between two or more elements thatare coupled with each other. Further, in one or more example embodimentsset forth herein, generally speaking, an element, component or modulemay be configured to perform a function if the element is capable ofperforming or otherwise structurally arranged to perform that function.

As used herein, a network element or node (e.g., a router, switch,bridge, etc.) is a piece of networking equipment, including hardware andsoftware that communicatively interconnects other equipment on a network(e.g., other network elements, end stations, etc.). Some networkelements in certain embodiments may comprise “multiple services networkelements” that provide support for multiple networking functions (e.g.,routing, bridging, switching, Layer-2 aggregation, session bordercontrol, Quality of Service, and/or subscriber management, and thelike), and/or provide support for multiple application services (e.g.,data, voice, and video). For purposes of the present patent application,a network element may be deployed in enterprise networks, intranets,extranets, Internet service provider networks, border networks, etc.Additionally or alternatively, a network element may also comprise insome embodiments a node or functionality deployed in indoor wirelesspersonal access networks (WPANs), home area networks (HANs), wirelesssensory networks, etc., wherein indoor wireless access solutions (e.g.,indoor mobile broadband) may be implemented with respect to various userequipment (UE) devices such as, e.g., smartphones, tablets, laptops, andthe like, in addition to providing access to any Internet Protocol (IP)addressable devices, appliances and sensors involving machine-to-machine(M2M) communications.

One or more embodiments of the present patent disclosure may beimplemented using different combinations of software, firmware, and/orhardware. Thus, one or more of the techniques and blocks shown in theFigures (e.g., flowcharts) may be implemented using code and data storedand executed on one or more electronic devices or nodes (e.g., asubscriber/user equipment (UE) device, an end station or endpoint, anetwork element, etc.). Such electronic devices may store andcommunicate (internally and/or with other electronic devices over anetwork) code and data using computer-readable media, such asnon-transitory computer-readable storage media (e.g., magnetic disks,optical disks, random access memory, read-only memory, flash memorydevices, phase-change memory, etc.), transitory computer-readabletransmission media (e.g., electrical, optical, acoustical or other formof propagated signals—such as carrier waves, infrared signals, digitalsignals), etc. In addition, such elements or nodes may typically includea set of one or more processors coupled to one or more other components,such as one or more storage devices (e.g., non-transitorymachine-readable storage media) as well as storage database(s), userinput/output devices (e.g., a keyboard, a touch screen, a pointingdevice, and/or a display), and network connections for effectuatingsignaling and/or data transmission. The coupling of the set ofprocessors and other components may be typically through one or morebuses and bridges (also termed as bus controllers), arranged in anyknown (e.g., symmetric/shared multiprocessing) or heretofore unknownarchitectures configured to interoperate with any Operating System (OS).Thus, the storage device or component of a given electronic device ornetwork element may be configured to store code and/or data forexecution on one or more processors of that element, node or electronicdevice for purposes of implementing one or more techniques of thepresent disclosure.

Referring now to the drawings and more particularly to FIG. 1, depictedtherein is an example network environment 100 including a radio accesssystem 102 for providing access with respect to information in 6LoWPANformat according to an embodiment of the present patent application. Forpurposes of the present patent application, the access system 102 may beconfigured to provide access relative to any number of IP addressabledevices that conform to the IEEE 802.15.4 specification and may bedistributed within an indoor space (e.g., a multi-level officebuilding). As part of a PAN, such devices may communicate amongthemselves (e.g., M2M communications), in addition being able tocommunicate with a higher-level network, e.g., an externalpacket-switched network such as the Internet. As will be described indetail hereinbelow, the access system 102 may be adapted to transport6LoWPAN data packets (hereinafter referred to as “6LO data”) to and fromone or more servers 122 coupled to an external packet-switched network,e.g., IP network 120, and may therefore be referred to as a 6LoWPAN dataaccess system (6LODAS). Further, in the example embodiment shown in FIG.1, the access system 102 may also provide wireless communications accessrelative to a cellular core network for mobile telephony and data,generally referred to as a core network 124, the signals for which maybe provided to elements known as active antenna elements (AAEs) that mayalso operate as 6LO data generators and/or collectors. In certainimplementations, the AAE elements may also be referred to as “radiohead” elements. In one particular embodiment, such an arrangement may beimplemented as a “radio dot” system (RDS) wherein the AAEs may bereferred to as radio dots (RDs) or radio dot (RD) elements for purposesof the present patent application.

In terms of an example generalized RDS architecture, the access system102 may be deployed as a cost-effective radio system, especially forindoor applications, by using a Digital Unit (DU) element 104 havingbaseband functionality that is interfaced with the cellular core network124 and coupled to one or more Radio Unit (RU) elements, e.g., RU 108,in a star topology. Each RU element may in turn be coupled to one ormore AAEs or RD elements, e.g., RD-1 114-1 to RD-M 114-M, each of whichmay be provided with one or more appropriate antenna elements, as willbe described in detail hereinbelow. Accordingly, from DU element 104 toRD elements 114-1 to 114-M, the access system 102 may span a“multi-level star” topology that may be adapted to permit daisy-chainingof the intermediary RU elements. It should be appreciated that such anarrangement allows dynamic baseband resource distribution among RDs inorder to support a flexible cell coverage architecture. It shouldfurther be noted that the DU element may also be referred to as aBaseband Unit (BBU) in the relevant art.

For connectivity and signal transmission, each RD element may be coupledto its corresponding RU element via a structured cabling system, e.g.,dedicated copper (Cu) cabling such as twisted pair cables or othermetallic cabling, for instance, that has suitable crosstalk and systemnoise properties. In one implementation, such cabling may comprisestandardized Category 5 or 6 or 7 cables (CAT 5/6/7 cables), and may beconfigured to transmit information as radio signals in a low frequencyor intermediate frequency (IF) band to reduce the cable loss.Accordingly, in one embodiment, RU to RD links 112-1 to 112-M shown inFIG. 1 may be referred to as Ethernet cabling communication links orconnections, or communication links in general. Further, power to RDelements may also be provided via the cabling system (e.g., power overEthernet or PoE), in addition supporting data transfer. Each RD elementincludes appropriate signal processing functionality for convertingbetween high frequency RF (radio frequency) signals and low frequency IF(intermediate frequency) signals in order to reduce the cable loss. Indownlink (DL) operation, the IF signal is received from the copper cableand up-converted to the RF signal at a desired RF band, and then the RFsignal is broadcast from the antenna to one or more UE devices (notshown in FIG. 1) that may be disposed in wireless communication with theRD element. As set forth previously, such wireless communication maypertain to cellular telephony and data communications with respect tothe cellular telephony network 124, and may therefore comprise bearerdata (e.g., voice, data, video, etc.) as well as associated controlplane signaling. In uplink operation (UL), the RF signals from the UEsare received at the RD element via the antenna and down-converted to thelow frequency IF signal. The IF signal is then transmitted through thecopper cable to the corresponding RU element, e.g., RU 108, to which theRD element is coupled.

Whereas the RU and RD elements are coupled in Ethernet-based structuredcabling system, each RU element (e.g., RU 108) is in turn coupled to theDU element 104 via a communication link 106 that is operable with CommonPublic Radio Interface (CPRI) protocol. With respect to the cellulartelephony/data communications, RU 108 is operative to convert betweenthe IF signals received from RD elements 114-1 to 114-M and the basebanddata flows (i.e., IQ data flows) that are compliant with the CPRIprotocol. Essentially, the cellular telephony/data information in the IFsignals is converted to baseband in-phase, quadrature (IQ) streams thatrepresent time domain samples of the baseband radio signals (i.e.,cellular communications radio bits), which are multiplexed along withother channels (e.g., Control/Management channel and Sync channel) andsent via the communication link 106 to DU 104. The basebandfunctionality of DU 104 is operative to demodulate the received IQ dataflows (for uplink operation) to data and forward the data to thecellular core network infrastructure 124. In downlink operation, thebaseband functionality of DU 104 is operative to modulate the datareceived from the cellular core network infrastructure 124 to a basebandsignal and convert it to a CPRI signal, i.e., multiplex the radio bitsas IQ data flows in a user plane of the CPRI protocol along with theother channels, and transmit the CPRI signal to the corresponding RUelement 108. Accordingly, for purposes of at least some embodiments ofthe present patent application, the communication link 106 disposedbetween DU and RU elements 104, 108 may be referred to as a firstcommunication link or connection whereas a communication link betweenthe RU and RD elements may be referred to as a second communication linkor connection. Furthermore, at least in some embodiments, the firstcommunication link 106 may be implemented as an electrical transmissionlink (when DU and RU elements 104, 108 are relatively closely located)or as an optical transmission link (for longer ranges). Additionally, anRU element (e.g., RU 108) may also be referred to as an Indoor RU (IRU)when deployed as part of an indoor wireless solution. In a still furthervariation, the DU and RU elements 104, 108 may be co-located orotherwise integrated as a single unit located in a cabinet of thepremises.

Irrespective of a specific implementation, the signals between the DUand RD elements of the access system 102 may be generally referred to as“RDS signals” that are transported according to the protocols and/orprocesses set forth above. In addition to carrying the data, theprocesses for effectuating end-to-end RDS communications also supportappropriate control and/or management channels for facilitatingfunctionalities such as RD configuration, control, monitoring, etc. Inaccordance with teachings of the present patent application, the controlchannels corresponding to the first and/or second communication links(i.e., links between the DU and RU elements and links between the RU andRD elements, respectively), may be advantageously adapted to transport6LO data to and from the RD elements 114-1 to 114-M. As set forth above,the first communication link 106 may be effectuated using the CPRIprotocol that provides a user plane data channel for transportinginformation as IQ data flows, which may be multiplexed in digital form(i.e., in bits) with control/management (C/M) messages that are packagedusing a High Level Data Link Control (HDLG) link layer mechanism. Thebuilt-in C/M channel accordingly provides suitable control signalingfunctionality between the DU element 104 and each RU element (e.g., RU108) coupled thereto.

With respect to the second communication links, i.e., links 112-1 to112-M, using Ethernet cabling and respectively disposed between RU 108and RD-1 114-1 to RD-M 114-M, the links include a dedicated controlchannel that may be provided at a frequency band separate from thesignal band or bands (i.e., out-of-band or sideband control signaling).A suitable modem (e.g., frequency-shift keying or FSK modem) may beprovided at each end of the link (at RU 108 and each RD 114-1 to 114-M,respectively) for transporting and extracting appropriate control andmanagement messaging information between the RU and RD elements.

For purposes of the present patent application, either the DU element104 or an RU element (e.g., RU 108) may be provided with suitable IPbridging functionality for interfacing with the external IP network viaan RDS gateway/router (RGR) as will be described in detail hereinbelow.In respect of the embodiment shown in FIG. 1, the bridging functionalityis provided as part of RU 108, which is interfaced with gateway/router118 via an IP link 116 for transporting 6LO data, i.e., data inaccordance with the mechanisms set forth athttps://datatracker.ietf.org/wg/6lo/charter/). Accordingly, a bridgingfunction (BF) module or block 110 is illustratively included in RU 108that effectuates 6LO data transport via second communication links 112-1to 112-M with respect to the RD elements 114-1 to 114-M. Secondcommunication links 112-1 to 112-M are therefore adapted to carry bothRDS signals and 6LO data. An alternative embodiment where the bridgingfunctionality is provided as part of a DU element is exemplified in FIG.2. First, an overview of the embodiment shown in FIG. 2 will be setforth, followed by a description of an example frequency band plan thatmay be used in the embodiments of FIGS. 1 and 2. Thereafter, a broadoutline of the respective bridging functionalities will be set forth,with examples of specific implementations following subsequently.

Turning to FIG. 2, an example network environment 200 including anRDS-based access system 202 exemplifies incorporation of a bridgingfunction (BF) module 206 within a DU element 204 for purposes oftransporting 6LO data according to another embodiment of the presentpatent application. Those skilled in the art will recognize that theaccess system 202 is illustrative of a more generalized implementationof an RDS system having a multi-level star topology wherein a single DUelement, e.g., DU 206, is operatively coupled to a plurality of RUelements, e.g., RU-1 212-1 to RU-N 212-N, via respective firstcommunication links or connections 210-1 to 210-N, each of the RUelements, in turn, being coupled to respective sets of RD elements usingcorresponding sets of second communication links or connections. Asillustrated, RU-1 212-1 is operative to support a first plurality of RDelements, RD-1 216-1 to RD-M 216-M, that are coupled to RU-1 212-1 viacommunication links 214-1 to 214-M, respectively. Likewise, RU-N 212-Nis operative to support Nth plurality of RD elements RD-1 220-1 to RD-L220-L that are coupled thereto via communication links 218-1 to 218-L.Similar to the embodiment shown in FIG. 1, DU 204 is interfaced to acellular core network 228 for effectuating wireless communications withrespect to one or more RD elements of the access system 202, whereinsuch wireless communications may comprise any known or heretoforeunknown cellular technologies, including, e.g., 3rd GenerationPartnership Project (3GPP)-compliant communications technologies asexplained elsewhere in the present patent application.

As the IP bridging functionality is provided as part of DU 204, agateway/router 222 is coupled thereto for interfacing with an externalpacket-switched network 224, e.g., a public IP network such as theInternet, for accessing one or more servers 226 with respect to 6LOdata. Because of the IP bridging at the head-end, i.e., DU 204, of theaccess system 202, both first and second communication links are adaptedto carry RDS signals and 6LO data. Further, similar to the embodimentshown in FIG. 1, first communication links 210-1 to 210-N disposedbetween the DU and RU elements in FIG. 2 may be implemented using theCPRI protocol and may therefore be referred to as CPRI links. Likewise,second communication links 214-1 to 214-M and 218-1 to 218-L disposedbetween the RU elements and respective sets of RD elements may beimplemented using the Ethernet cables, which may be referred to asEthernet cable communication links or Ethernet cable links. It shouldtherefore be appreciated that the baseband functionalities of the DU andRU elements shown in FIG. 2 are substantially similar to thefunctionalities of the DU and RU elements described hereinabove withrespect to FIG. 1 and the description of the variousfunctional/structural features set forth in the two Figures may beapplied relative to each other, mutatis mutandis.

FIG. 3 depicts an example frequency band plan 300 for use with anembodiment of a 6LODAS of the present patent application such as, e.g.,the embodiments shown in FIGS. 1 and/or 2 set forth above, foreffectuating communications on an Ethernet cable link disposed betweenRU and RD elements. As alluded to previously, the Ethernet cable basedcommunication links are adapted to carry signals in an intermediatefrequency (IF) band to reduce cable loss (e.g., a frequency range ofless than 200 MHz or thereabouts, with a bandwidth of 40-80 MHz). A Syncsignal 302 is provided effectuating frequency/phase synchronization,etc., followed by a frequency band for uplink communications (i.e., fromRD elements to RU elements), referred to as UL band 304. Anotherfrequency band, DL band 306, is provided for downlink communications(i.e., from RU elements to RD elements), which is the followed by acontrol signal band 308 for effectuating control/management messages. Inthe example embodiment of FIG. 1 where the IP bridging is done in RU108, the control signal band 308 may be appropriately modulated forcarrying 6LO data to and from the RD elements 114-1 to 114-M. Further,the Ethernet cable communication links in embodiments of either FIG. 1or FIG. 2, or both, may also support remote powering of the RD elements,i.e., power over Ethernet or PoE, in certain implementations, whichprovides for DC power supply from the RU elements coupled thereto.

Taking reference to FIG. 4, depicted therein is a block diagram of anactive antenna element (AAE) or a radio dot (RD) element 400 including asensor component 410 according to an embodiment of the present patentapplication. In one example implementation, the sensor 410 associatedwith RD 400 may be configured to sense or otherwise measure one or moreambient or environmental variables such as, including but not limitedto, temperature, moisture, light, motion, pressure, and the like. Sensor410 may therefore comprise a temperature sensor, a moisture sensor, alight sensor, a pressure sensor, or a motion sensor, etc., or anycombination thereof. Additionally, sensor 410 may be illustrative ofvarious biological/physiological sensors, chemical sensors,environmental quality sensors (e.g., air/water quality), etc. Further,as part of an IoT/IoE-based architecture, the sensor element 410 may beconfigured to obtain or otherwise generate sensor data from anyInternet-connected appliance or physical device and may comprise,without limitation, measurement/instrumentation equipment, sensingequipment, medical device/instrumentation, intelligent home/automobiledevice/instrumentation, smart metering instrumentation, gaming/homeentertaining equipment, computing/communication equipment such aslaptops, tablets, desktops, mobile communication devices, and the like,depending on the specific application environment and appropriatepackaging/integration. Accordingly, the term “measurement variable” mayencompass any variable(s) or a combination thereof that may be measuredor otherwise sensed by the sensor component 410 for purposes herein.

As described previously, RD 400 may be provided with appropriate cabling402 comprising one or more twisted pair cables for carrying RDS signals,including control channel messages, to and from an RU element associatedtherewith. A cable/copper front-end (Cu-FE) block or module 404interfaced with the cabling 402 may be configured formultiplexing/de-multiplexing various signals of the IF frequency band(e.g., Sync signals, UL/DL signals and control channel signals). A radiofront-end or FE block 406 is operative for IF/RF conversions (IF-to-RFfor DL transmission and RF-to-IF for UL transmission) and may beinterfaced with one or more antennas 408, depending on transceiver(Tx/Rx) circuitry and frequency filtering implementations. A Sync block412 extracts the Sync signal transmitted from the RU side andsynchronizes the RD element's clock signal with the accessnetwork/system's clock. A modem (e.g., FSK modem) 414 is operative toperform modulation and demodulation of the signals, including controlchannel signals, under control of a suitable processor 416 (e.g., amicrocontroller or microprocessor), to and from the RU side of theaccess network/system, as will be described in detail below. In general,processor/controller 416 may be configured to execute appropriateprogram instructions for controlling the RD element 400 according to themessages received from the RU side and for effectuating 6LO dataprocessing. Processor/MCU 416 may also execute or otherwise effectuatesuitable control channel message processing or packaging 419 (e.g.,according to RU-RD control channel messaging) in conjunction with modem414. Further, depending on implementation, sensor 410 may or may notinclude appropriate functionality for generating sensor data that iscompliant with the 6LoWPAN specification, which functionality isillustratively shown as an optional 6LO stack 411. Accordingly, RD 400may also optionally include a 6LO data functionality, generally referredto as (re)packager 418 for packaging, repackaging, unpackaging, etc.,that is executed under control of processor 416 for transmission to/fromthe RU side in certain variations. Additionally, it should beappreciated that RD 400 may be provided with suitable powering circuitry(not specifically shown) for effectuating remote powering (e.g., PoEimplementation).

FIGS. 5 and 6 depict block diagrams of an AAE or RD element 500 and 600,respectively, including a 6LO access point (AP) 518 or 618 according toadditional embodiments of the present patent application. In general, a6LO AP may be implemented to provide the access to wireless sensorsand/or wireless sensor gateways that collect the data from a pluralityof sensors. One skilled in the art will recognize upon reference heretothat the various components and blocks of RD 500 and RD 600 aresubstantially similar to the components and blocks described above withrespect to FIG. 4. Accordingly, the description set forth above withrespect to certain features of RD 400 is equally applicable to theembodiments shown in FIGS. 5 and 6, mutatis mutandis. As a result, aseparate description of features referenced by reference numerals502-516 in FIG. 5 and reference numerals 602-616 is not set forthherein. Keeping that in mind, it should be appreciated that 6LO AP 518of RD 500 in FIG. 5 may be provided with an antenna element 520 that isseparate from the radio FE antenna 508 for communicating with other 6LOsensors, 6LO devices, and/or 6LO gateways. On the other hand, theembodiment shown in FIG. 6 employs a common or shared antenna 608 thatis used by both radio FE block 606 and 6LO AP 618. A suitable filteringblock 620 is therefore provided as part of RD 600 for separating thefrequency bands used for the two types of wireless communications (e.g.,3GPP versus 6LoWPAN communications). For example, a 2.1 GHz antenna maybe adapted for use with a 2.4 GHz 6LO signal, although the antennaefficiency may be degraded somewhat. To address such implementations andassociated issues, it should be appreciated that appropriate antennadesigns may be required (e.g., a wideband antenna that is adapted tosupport more bandwidth covering neighboring 6LO bands). Although asuitable band filter may be integrated within radio FE block 606 and/or6LO AP block 618 for separating the frequency bands used in wirelesscommunications via the shared antenna 608, an optional externalfiltering block may be provided instead as part of RD 600, e.g., filter620 illustrated in FIG. 6.

To the extent the data associated with 6LO AP elements 518 and 618 isnot 6LoWPAN compliant, processors 516, 616 in FIGS. 5 and 6,respectively, may be configured to execute a 6LO data functionality,analogous to a variation of the embodiment depicted in FIG. 4, forpackaging, repackaging, unpackaging, etc., with respect to the gatheredor collected source/sense data. 6LO data packets may be (re)packaged ascontrol channel messages for transmission between the RD and RU elementsvia appropriate Ethernet cabling communication links as will bedescribed below. In addition, it should be understood that the accesspoints may be configured to effectuate a 6LO interface of any Layer 2(L2) technology that runs the 6LO stack. Accordingly, the antennaembodiments set forth herein can be any of the IEEE 802.15.4g, IEEE802.11n or Z-wave antenna elements, and the 6LO stack of exemplary RDSimplementations may therefore be executed by a suitable L2 interface forcapturing the 6LO data signals. Such 6LO example implementations mayalso comprise ZigBee, Z-wave and BT-le (BlueTooth low energy)implementations.

Turning now to FIG. 9, depicted therein is a flowchart of blocksrelative to various steps and/or acts of a process 900 that may takeplace at an RU element, e.g., RU 108, for effectuating data transferwith respect to the embodiment shown in FIG. 1, wherein IP bridging iseffectuated by way of the BF module 110. In the example embodiment shownin FIG. 9, a downlink process is illustrated whereby 6LO data packetsreceived from a gateway or border router (e.g., router 118) aretransmitted to a destination RD element which may comprise any of theforegoing embodiments described above (i.e., RD with a sensor, RD with a6LO access point, with one or more antenna elements, and with or withouta separate or shared antenna arrangement, or any combination thereof).When the RU element receives 6LO data packets from the gateway routercoupled to the external packet-switched network, they may be processedappropriately (e.g., decapsulation, unpacking, etc.), whereupon thedestination IP address of the received packets may be examined fordetermining the destination RD element's address, as exemplified byblocks 902 and 904. In one implementation, such determination may beeffectuated by way of maintaining an IP-to-RD address mapping database(e.g., a forwarding table) and querying the database as needed.Repackaging functionality of the BF module is operative to repackage the6LO data packets as a control channel message in a format specified forthe control channel associated with the Ethernet cable communicationlink disposed between the RU and RD elements (block 906). Thereafter,the repackaged 6LO data packets are transmitted as an RD-RU controlchannel message to the appropriate RD element based on the forwardingtable determination (block 908). Accordingly, the 6LO data packets maybe taken as the payload of the control channel messages.

In an embodiment where the IP bridging takes place at a DU element,e.g., DU 204 in FIG. 2, a two-stage (re)packaging process may berequired. FIGS. 11A and 11B depicts a flowchart of blocks relative tovarious steps and/or acts of such a process 1100A/1100B that may takeplace at DU and RU elements, respectively, for effectuating datatransfer with respect to the embodiment shown in FIG. 2. When a DU orBBU element receives 6LO data packets from a gateway router coupled tothe external packet-switched network, they may be processed as neededand the IP destination address field of the packets is examined in orderto determine a corresponding RD element's address to which the packetsare ultimately destined as well as the associated RU element's addressthat the packets need to traverse (blocks 1102 and 1104). In oneimplementation, the DU element may maintain suitable IP-to-RD andRU-to-RD address mapping databases for effectuating a two-step queryingprocess. Alternatively, where the address mapping databases areintegrated as a single IP-to-RU-to-RD database or table, querying may beeffectuated accordingly to determine or otherwise obtain the next hop RUelement's address. Repackaging functionality of the BF module executingat the DU element is operative to repackage the 6LO data packets as aCPRI control/management (C/M) channel message in a format specified forthe CPRI protocol. Thus, the 6LO data packets may be taken as thepayload of the CPRI C/M channel messages for this segment ofcommunications. Block 1106 of FIG. 11A is illustrative of suchCPRI-compliant packaging and may be referred to as the first(re)packaging stage. Thereafter, the repackaged 6LO data packets aretransmitted to the corresponding RU element based on the forwardingtable determination(s) as a CPRI C/M message via the CPRI communicationlink disposed therebetween (block 1108). In one implementation, the CPRIC/M message packaged with the 6LO data may also include the RD element'saddress to which the 6LO data packets are destined. It should beappreciated that in such an arrangement, the intermediary RU element maynot be required to maintain a separate IP-to-RD address mapping databaseand, accordingly, another address mapping query may be avoided thereat.On the other hand, where the CPRI C/M messages do not include an RDelement's address, a secondary address mapping query may be required bythe RU element.

Reference numeral 1100B of FIG. 11B generally refers to a process at theRU element (e.g., RU-i 212-i, i=1, 2, . . . , N) that receives CPRI C/Mmessages packaged with 6LO data from the DU element 204. Upon receivingthe (re)packaged 6LO data packets from the DU element as CPRI C/Mmessages, the destination of the RD element is determined or otherwiseobtained (e.g., included in the C/M message) after unpacking the C/Mmessage, as exemplified at blocks 1110 and 1112. Thereafter, the 6LOdata packets are (re)packaged as a control channel message in a formatspecified for the control channel associated the Ethernet communicationlink, which may be referred to as the second (re)packaging stage (block1112). The RU-RD control message(s) including the (re)packaged 6LO datapackets are transported to the corresponding RD element via the Ethernetcable communication link disposed therebetween (block 1114). Similar tothe embodiment described hereinabove with respect to FIG. 9, adestination RD element in the embodiment of FIGS. 11A and 11B maycomprise any of the RD implementations described previously.

FIG. 10 depicts a flowchart of blocks relative to various steps and/oracts with respect to a process 1000 that may take place at an RD elementupon receipt of (re)packaged 6LO data from an RU element. It should beappreciated that process 1000 is agnostic as to whether the 6LO data wasbridged at RU or at DU because irrespective of where the bridging isdone, the RD element receives the (re)packaged 6LO data as a controlchannel message relative to the RU-RD link in the embodiments of FIGS. 1and 2. In one implementation, such a control channel associated with theRU-RD links may be proprietary. In other variations, the control channelmay be compliant with respect to known standards. As an example, theframe structure for the control channel may comply with the IEEE802.15.4g specification and the message may comply with HDLC. Regardlessof whether standards-compliant or proprietary implementation, uponreceiving the RU-RD control message(s) including 6LO data, the RDelement is operative to unpack the control message(s) and obtain the 6LOdata packets after suitable demodulation (blocks 1002 and 1004).Thereafter the 6LO data packets may be presented or otherwise deliveredto a suitable 6LO module or unit for further processing, e.g.,effectuating a DL transaction relative to a sensor (whether integratedwithin the RD element or otherwise), delivery via a 6LO access point toone or more 6LO devices associated with the RD element, and the like, asexemplified at block 1006.

One skilled in the art will recognize upon reference hereto that whereasFIGS. 9 and 11A/11B describe bridging and (re)packaging operationsrelative to DL transactions, the bridging functionalities of RU and DUelements are also operative to execute similar processes—but generallyin reverse—for effectuating 6LO bridging with respect to UL transactions(i.e., transmission of 6LO data packets from the RD elements to RU andon to DU elements of a 6LO access system. In general, a 6LO unit in theRD is operative to (re)package the packets according to the RU-RDcontrol channel message specification and transmit upstream to the RUelement. Upon receipt, the RU element unpacks the control channelmessage and may forward the 6LO data to an RDS gateway/router if the RUelement is where IP bridging takes place. The RU element may repackagethe 6LO data according to 6LoWPAN with source IP address associated withthe RD element (e.g., where RD is integrated with a sensor that does notimplement a full 6LoWPAN stack). In the case where a DU element executesIP bridging, the intermediary RU element unpacks the RU-RD controlchannel message including the 6LO data and repackages them intoCPRI-compliant C/M messages for transmission to the DU element. Uponreceipt, the DU element unpacks the C/M message and forwards the 6LOdata to an RDS gateway/router coupled thereto for transmission to a 6LOserver. Similar to the RU element, the DU element may repackage the 6LOdata according to 6LoWPAN with source IP address associated with the RDelement where the source data is not 6LoWPAN-compliant (e.g., datagenerated/gathered by a sensor that does not implement a full 6LoWPANstack and which data has not been processed at the RD element to be6LoWPAN-compliant). Additional details, implementations and variationsrelative to the foregoing UL bridging processes will be set forth belowin particular reference to FIGS. 12A-12B.

Taking reference to FIGS. 7A-7C, depicted therein are block diagrams ofembodiments of an RDS gateway/router, a DU/BBU element and an RU elementadapted to interoperate with each other for implementing a 6LO accesssystem of the present disclosure. Basically, the embodiments depicted inFIGS. 7A-7C represent structural block diagrams adapted to effectuate atleast some of the processes set forth in the present patent application.Reference numeral 700A of FIG. 7A generally refers to a gateway routerthat may be configured as a device for effectuating point-to-point (P2P)connectivity between itself and the IPv6 destination elements in respectof an example 6LO access system. One or more processors 702 coupled tosuitable memory 704 (e.g., nonvolatile or persistent memory) areoperable in conjunction with various other modules and/or databasestructures for realizing the overall functionality of the gateway router700A. In one arrangement, IoT/IoE/M2M communications may be implementedas an end-to-end 6LoWPAN-compliant communication system, meaning eachendpoint has its own IPv6 address and 6LO media access control (MAC)address. It should be realized that the MAC address length could be ofvariable length/size that a 6LO technology allows for achievingcompliance with the 6LoWPAN stack. Accordingly, an example system mayinvolve one or more of the following implementation features. Forexample, each access system element (DU, RU, or RD) may be provided itsown IPv6 address assigned by the gateway router 700 using P2Pconnections. A DU or RU element may be considered as a radio end unit(REU) depending on where the IP bridging takes place. If DU implementsbridging, a P2P connection may involve a path that uniquely defines aparticular router-DU-RU-RD combination. Likewise, if RU implementsbridging, a P2P connection may involve a path that uniquely defines aparticular router-RU-RD combination. In general, therefore, a P2Pconnection may involve a unique router-REU-RD address combination. Also,each IoT/IoE/M2M network gateway or access point or 6LO device may beprovided with a prefix (Px) and an RD element may be configured tohandle devices and access points that are under the same prefix (Px).Further, an RD element may be assigned an IPv6 address based on Px and aMAC address compliant with the 6LoWPAN specification. Such addresses maybe maintained in a database associated with the DU or RU elements or therouter 700A (if the router is directly coupled to the RD elementswithout any bridging at DU/RU, in which case the router is also an REU).Packets from a IoT/IoE/M2M network gateway or access point or 6LO deviceare directed to the correct RD element and then mapped to thecorresponding IPv6/MAC address combination in the REU which is operableto create a P2P connection to the gateway router 700A for sendingsuitably encapsulated data.

For purposes of the present patent application, the gateway router 700Amay be configured to effectuate the following features including but notlimited to: executing a routing protocol toward the IP network;advertising as a default IPv6 router toward the 6LO access system'sendpoints; creating P2P connectivity for each RD element and associatedREU; conversion between 6LoWPAN and IPv6 data packets as needed;maintaining a list of IPv6 and MAC addresses of the RD elements; andmaintaining a dedicated interface for IPv6 and IPv4 networks; andconversion between IPv6 and IPv4 data packets as needed. Additionally,the gateway router 700A may be configured to operate as a main IPgateway between the RDS-based 6LO access system and one or more IPv6networks. Accordingly, the gateway router 700A includes a 6LO-to-IPv6adaptation layer 710 that defines how the IPv6 packets are carried overa constrained 6LoWPAN network implemented according to IEEE 802.15.4specification. Because the protocol data unit (PDU) size of IEEE802.15.4 is 127 octets whereas the maximum transfer unit (MTU) size ofIPv6 packets is 1280 octets, the adaptation layer 710 provides suitablefragmentation and reassembly for IPv6 packets, while providing for aheader compression scheme for reducing the size of the IPv6 header.Thus, the gateway router 700A is operative to perform the compressionand decompression of IPv6 packets as well as supporting mapping between16 bit short addresses and the IPv6 addresses for both the external IPv6networks and a 6LoWPAN network.

A P2P connection and routing database 712 comprising the following isillustrative:

TABLE 1 RU/DU RD/sensor Next Hop for Destination IP and MAC IP and MACOutbound IPv6 P2P Link addresses addresses hop Px/address . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .

In general, database 712 may include unique address mapping combinationsfor facilitating corresponding P2P connections with respect to an RDS.By way of an implementation, IP and MAC addresses of an RD/sensor maycomprise virtual addresses because the RD may not have IP/MAC processingfunctionality. The system may or may not need the IP and MAC addressesof an RD/sensor for routing. That being said, functioning as the lasthop router, RGR 700A needs to send the packets to the RD/sensor (orsensor's gateway) for 6LO networking purposes. It should be appreciatedthat RU and RD elements do not have to have IP and/or MAC addresses. RUelements may be addressable in CPRI, that is, RU addresses may comprisea port number, an RU number, etc. RD elements are connected on differentEthernet cables in an RDS; so it may be easier to address them by portnumbers as well. Particularly, where each RD may be modeled as a“sector”, the RD address may comprise a sector number.

By way of illustration, the gateway router 700A includes appropriateTx/Rx circuitry and interfaces for IPv6 connectivity 706, optional IPv4connectivity 708 as well as 6LoWPAN connectivity 714. The gateway router700A may also interface with an IPv4-transition or conversion block incase IPv6 data needs to be sent via an IPv4 network. Accordingly, block708 is also illustrative of an IPv6/IPv4 tunnel mechanism. Since thegateway router 700A is capable of understanding 6LO data packets andconverting the 6LoWPAN adaptation layer into a full IPv6 header, theIPv6 header's source address field contains the source address of thesending RD/sensor wherein the destination IPv6 address field is thedestination IPv6 address carried in the original 6LO data. The gatewayrouter 700A further includes the functionality for mapping the sendingRD/sensor's IPv6 address with the appropriate P2P link, which is helpfulwhen the data packets flow in the reverse direction (i.e., DLtransactions).

An example RU element 700B shown in FIG. 7B is illustrative of the RUelements depicted in the embodiments of FIG. 1 or 2 describedhereinabove, suitably modified as needed. One or more processors 752coupled to suitable memory 754 (e.g., nonvolatile or persistent memory)are operable in conjunction with various other modules and/or databasestructures for realizing the overall functionality of RU 700B accordingto an embodiment of the present patent application. When implementedwith IP bridging, a BF and (re)packaging module 756 may be included inRU 700B for effectuating at least some of the processes set forthhereinabove, which may be realized upon execution of programinstructions or code portions under control of the processor(s) 752. Asdiscussed previously, an IP address may be assigned with respect to eachRD/sensor/6LO unit for effectuating 6LO data flow in P2P connections.Accordingly, a forwarding table or an IP association table or moregenerally a mapping database 758 is operable for maintaining mappingrelationships between IP addresses and RD addresses (e.g., MACaddresses, RD numbers, port numbers, or sector numbers, etc.). Theforwarding table 758 may be formulated as several pairs of“IP_(X)-RD_(Y)”, meaning a packet having the destination IP address ofIP_(X) is to be directed to the RD having the address RD_(Y). Asdescribed above, RD addresses may be provided in one implementation asproprietary addresses (e.g., port numbers, sector numbers or some otheridentifying indicia), in addition to having virtual IP/MAC addresses.Further, where the source data coming from the RD elements is not6LoWPAN-compliant, appropriate packaging may be performed by the RUelement 700B so that proper 6LO data packets (including source IPaddresses associated with the RD elements) may be forwarded to a gatewayrouter associated therewith. If RU 700B is not implemented as a bridgingelement, the functionality of mapping database 758 may not be necessaryand instead a (re)packaging of data between CPRI C/M messages and RU-RDcontrol messages is performed as an intermediary element between DU andRD elements. Accordingly, appropriate Tx/Rx circuitry and interfaces for(optional) gateway router connectivity 762 (if bridging is done at RU700B), DU/CPRI connectivity 760 and RD/Ethernet cable link connectivity764 may be provided as part of RU 700B.

An example network element 700C is shown in FIG. 7C that is illustrativeof the DU (or BBU) elements depicted in the embodiments of FIG. 1 or 2described hereinabove, suitably modified as needed depending on whetheror not IP bridging takes place thereat. Further, network element 700 cmay also be illustrative of a BBU element in a PRAS implementationdescribed hereinbelow. One or more processors 782 coupled to suitablememory 784 (e.g., nonvolatile or persistent memory) are operable inconjunction with various other modules and/or database structures forrealizing the overall functionality of DU 700C according to anembodiment of the present patent application. When implemented with IPbridging, a BF and (re)packaging module 786 may be included in DU 700Cfor effectuating at least some of the processes set forth hereinabove,which may be realized upon execution of program instructions or codeportions under control of the processor(s) 782. Because DU 700C isIP-based, the 6LO data of a 6LO access system can use the radio backhauland core network to get connected with the appropriate 6LO server.Similar to the functionality of an RU element, the functionality of DU700C may include assignment of IP addresses with respect to theRD/sensor/6LO units of the 6LO access system for effectuating 6LO dataflow via P2P connections. One or more forwarding tables or IPassociation tables or more generally a mapping database 788 may beconfigured for maintaining mapping relationships between IP addresses,RD addresses (e.g., MAC addresses, RD numbers, port numbers, or sectornumbers, etc.) and RU addresses. The forwarding table 788 may beformulated as several pairs of “IP_(X)-RU_(Y)-RD_(Z)”, meaning a packethaving the destination IP address of IP_(X) is to be directed to the RDhaving the address RD_(Z) via an intermediary RU having the addressRU_(Y). Further, where the source data coming from the RD elements isnot 6LoWPAN-compliant, appropriate packaging may be performed by the DUelement 700C so that proper 6LO data packets including RD elements'source IP addresses may be forwarded to a gateway router associatedtherewith. Additionally, the (re)packaging functionality of DU 700C isoperative to (re)package 6LO data as CPRI C/M messages for DLtransmission to one or more RU elements coupled thereto as describedpreviously. Accordingly, appropriate Tx/Rx circuitry and interfaces for(optional) gateway router connectivity 792 (if bridging is done at DU700C), RU/CPRI connectivity 794 and cellular core network connectivity790 may be provided as part of DU 700C.

FIG. 8 depicts an example process flow 800 illustrating data transferbetween a 6LODAS element and associated router using point-to-pointconnectivity and encapsulation according to an embodiment. Referencenumerals 808-1 to 808-K refer to a plurality of 6LODAS endpoint elements(e.g., RDs, RDs integrated with sensors, RDs integrated with 6LO accesspoints, etc.) that generate or receive 6LO data via P2P connections806-1 to 806-K maintained between a gateway router 802 and across an REU804 (i.e., either an (I)RU or a DU element). A DL transmission 803 froman IP network (IPv6 or IPv4) and an UL transmission 805 to the IPnetwork (IPv6 or IPv4) with respect to IPv6 payload 810 are illustratedrelative to the gateway router 802 which facilitates suitableencapsulation/decapsulation of 6LO data 812 with appropriate addressheaders for transport via the P2P connections. In an example ULtransaction (from the RD/sensor endpoint to the network), the REUelement 804 decapsulates the packets, packages the data into 6LoWPANformat (if not already in that format) and forwards the 6LO data orencapsulates/maps the data to IPv6 format depending on itsfunction/configuration. The forwarding/adjacency tables of the gatewayrouter 802 are operative to determine the next hop into the IP networkfor subsequent transmission.

FIGS. 12A and 12B depict flowcharts of blocks relative to additionaldetails with respect to various steps and/or acts that may take placewithin a 6LO access network system for effectuating 6LO data ULtransactions according to one or more embodiments of the present patentapplication. Source data generated, measured, or otherwise obtained atan endpoint (e.g., RD/sensor, 6LO access point, 6LO device, a WiFiaccess point running a 6LO stack, etc., which may be processed orpre-processed as may be needed in certain implementations, exemplifiedat block 1202) may or may not be 6LoWPAN compliant and depending onwhere IP bridging takes place within the 6LO access network, a number ofvariations may be provided for transmission of the source data acrossthe access network. Further, because the source data is repackaged asRU-RD control messages (regardless of whether 6LoWPAN compliant), anddepending on where the 6LoWPAN compliance is achieved, additionalvariations may be provided. For purposes of the present patentapplication, the various permutations and/or combinations of potentialsource data treatment processes may be broadly grouped as three options,wherein not all treatment processes or steps will be necessary forpracticing a specific embodiment. For example, a determination may bemade at the endpoint (e.g., RD) to verify if the source data is 6LoWPANcompliant (block 1203). Process flows relating to Options 1 and 3 showngenerally at 1200A in FIG. 12A are based on either achieving 6LoWPANcompliance within the RD element or upon the determination that thesource data is already 6LoWPAN compliant. Process flows relating toOption 2 are shown generally at 1200B in FIG. 12B and are based onachieving 6LoWPAN compliance either at DU or at RU depending on where IPbridging takes place.

With respect to Option 1 (block 1204A), as the source data is determinedto be non-compliant, it is (re)packaged as 6LoWPAN-compliant datapackets at the RD element (block 1206). This step is avoided in Option 3(block 1204C) because it is determined that the source data is alreadycompliant (blocks 1203 and 1205). Regardless of whether the source datais already compliant or (re)packaged as 6LoWPAN-compliant data, the datais (re)packaged into a control channel message format for transmissionto an RU element coupled to the RD element via an Ethernet cablecommunication link (blocks 1208 and 1210). A determination is madewhether the RU element is operative as an IP bridging element in the 6LOaccess system (block 1212). If so, the RU element separates the cellularradio communication signals (in analog form), if any, relative to thewireless communications (e.g., 2G/3G/4G/5G communication signals, whichare converted to the CPRI signals and transmitted to the DU element) andsends the extracted 6LO data to a gateway router coupled thereto via asuitable P2P pathway as described previously (block 1214). The 6LO datapackets may be reassembled via an IPv6 adaptation layer for transmissionto an external IPv6 network (block 1224).

If the bridging is not done in the RU element, the 6LO data packets are(re)packaged as a CPRI C/M message and transmitted to the DU elementcoupled thereto via a CPRI communication link (blocks 1216 and 1218). Asthe DU element is operative to perform IP bridging (block 1220), anyradio bits relative to the baseband wireless communications (e.g.,2G/3G/4G/5G communications involving voice, data, or both) are separatedfor interfacing with the core network and the extracted 6LO data packetsare transmitted to a gateway router coupled thereto via a suitable P2Ppathway as described previously (block 1222) for transmission to anexternal IPv6 network (block 1224).

With respect to Option 2 (block 1204B), the source data (which maycomprise non-compliant data) is packaged into a control channel messageformat for transmission to an RU element coupled to the RD element viaan Ethernet cable communication link (blocks 1252 and 1254). Adetermination is made whether the RU element is operative for IPbridging in the 6LO access system (block 1256). If so, the RU elementseparates the IF radio signals, if any, relative to the wirelesscommunications (e.g., e.g., 2G/3G/4G/5G communication signals, which areconverted to the CPRI signals and transmitted to the DU element),(re)packages the source data as 6LoWPAN-compliant data and sends the 6LOdata to a gateway router coupled thereto via a suitable P2P pathway asdescribed previously (blocks 1258 and 1260). As before, the 6LO datapackets may be reassembled via an IPv6 adaptation layer for transmissionto an external IPv6 network (block 1272).

If the RU element is not a bridging element in the 6LO access system,the source data may be (re)packaged as a CPRI C/M message andtransmitted to the DU element coupled thereto via a CPRI communicationlink (blocks 1262 and 1264). As the DU element is operative to performIP bridging, any IQ data flows relative to the wireless communications(e.g., 3GPP communications involving voice, data, or both) are separatedfor interfacing with the cellular core network and the extracted sourcedata may be packaged as 6LO data packets, which are transmitted to agateway router coupled thereto via a suitable P2P pathway as describedpreviously (blocks 1268 and 1270) for transmission to an external IPv6network (block 1272).

FIG. 13 depicts an example network environment 1300 including aPico-RRU-based access system (PRAS) 1302 for accessing 6LoWPAN dataaccording to another embodiment of the present patent application. APRAS implementation may involve a plurality of small remote radio units(RRUs) (which may be referred to as pico-RRUs, usually abbreviated aspRRUs or PRRUs) that are integrated with antennas for indoor deployment,which may be configured to serve as 6LO data endpoints. Similar to theembodiment depicted in FIG. 2, a BBU element 1304 that interfaces withone or more cellular core networks 1328 is operative for effectuating IPbridging functionality (BF) 1306 for transporting 6LO data to and from agateway router 1322 relative to one or more 6LO servers 1326 associatedwith an external IP network 1324. Analogous to the RU elements shown inFIG. 2, PRAS 1302 comprises a plurality of remote hub (RHUB) elements1312-1 to 1312-N coupled to BBU 1304 via corresponding CPRIcommunication links 1310-1 to 1310-N. Further, each RHUB element may beconfigured to serve a corresponding set of PRRUs, wherein each PRRU iscoupled to the RHUB element via Ethernet cabling. In contrast to theembodiment of FIG. 2, however, signal transport via the Ethernet cablingis performed in accordance with the CPRI protocol, wherein RHUB isoperative to aggregate the IQ data flows from/to the PRRUs connected.Accordingly, it should be appreciated that in PRAS 1302 both BBU-RHUBand RHUB-PRRU communications are effectuated using CPRI, and therespective links may therefore be referred to as “first CPRIcommunication links” and “second CPRI communication links”. By way ofillustration, RHUB-1 1312-1 is coupled to PRRU-1 1316-1 to PRRU-M 1316-Mvia second CPRI communication links 1314-1 to 1314-M. Likewise, RHUB-N1312-N is coupled to PRRU-1 1320-1 to PRRU-L 1320-L via another set ofsecond CPRI communication links 1318-1 to 1318-L. End-to-end connectionsin PRAS 1302 are therefore CPRI-based, although such an implementationcan be more expensive and may require higher power consumption than theembodiments previously described in respect of FIGS. 1 and 2.

6LO data may be transmitted in PRAS 1302 using CPRI C/M messages for(re)packaging the 6LO data for both UL and DL transactions fromend-to-end. Keeping this distinction in mind, accordingly, thedescription provided for DU elements, RU elements and RD elements,including their respective variations, etc. may be equally applied toBBU elements, RHUB elements and PRRU elements of PRAS 1302, mutatismutandis, in addition to suitably configuring the functionality ofgateway router 1322 similar to that of the router embodiments describedabove.

Turning to FIG. 14, depicted therein is a flowchart of blocks relativeto an example process 1400 that may take place for effectuating 6LO datatransfer with respect to a PRAS embodiment such as one shown in FIG. 13.At block 1402, a BBU element receives 6LO data packets from a routercoupled to an external packet-switched network. As set forth previouslywith respect to RDS-based embodiments, the data packets may be processedor pre-processed appropriately (e.g., decapsulation, unpacking, etc.),whereupon further operations may be executed. Upon examining adestination IP address of the 6LO data packets, a determination may bemade regarding an address of at least one PRRU element to which the 6LOdata packets are to be delivered (block 1404). Corresponding to theaddress of the at least one PRRU element, an address of an intermediaryRHUB element may be made (block 1406). Similar to the embodiments setforth previously, appropriate database querying steps may be executed todetermine the addresses (e.g., querying IP-to PPRU address mappingtable(s), PPRU-to-RHUB address mapping tables(s), and/orIP-to-PRRU-to-RHUB address mapping table(s)). The BBU element(re)packages the 6LO data packets in a format specified for acontrol/management (C/M) channel associated with a first CPRIcommunication link or connection disposed between the BBU and RHUBelements, which are then transmitted to the RHUB element in a first CPRIC/M message via the first CPRI communication link (blocks 1408 and1410). Upon receiving the repackaged 6LO data packets in the first CPRIC/M message from the BBU element, the RHUB element unpacks the firstCPRI C/M message and obtains the at least one PRRU element's address towhich the 6LO data packets are to be delivered (block 1412).Subsequently, the RHUB element (re)packages the 6LO data packets in asecond CPRI C/M message and transmits the second CPRI C/M message to theat least one PRRU element via a second CPRI communication link orconnection (block 1414).

Whereas the process flow 1400 describes a DL transaction in PRAS 1300, asimilar process in reverse may be employed for effectuating ULtransactions, incorporating any number of variations analogous to theRDS-based embodiments previously described, mutatis mutandis. As aresult, a separate description of features relative to UL transactionsin PRAS 1300 is not set forth herein.

In the above-description of various embodiments of the presentdisclosure, it is to be understood that the terminology used herein isfor the purpose of describing particular embodiments only and is notintended to be limiting of the invention. Unless otherwise defined, allterms (including technical and scientific terms) used herein have thesame meaning as commonly understood by one of ordinary skill in the artto which this invention belongs. It will be further understood thatterms, such as those defined in commonly used dictionaries, should beinterpreted as having a meaning that is consistent with their meaning inthe context of this specification and the relevant art and may not beinterpreted in an idealized or overly formal sense expressly so definedherein.

At least some example embodiments are described herein with reference toblock diagrams and/or flowchart illustrations of computer-implementedmethods, apparatus (systems and/or devices) and/or computer programproducts. It is understood that a block of the block diagrams and/orflowchart illustrations, and combinations of blocks in the blockdiagrams and/or flowchart illustrations, can be implemented by computerprogram instructions that are performed by one or more computercircuits. Such computer program instructions may be provided to aprocessor circuit of a general purpose computer circuit, special purposecomputer circuit, and/or other programmable data processing circuit toproduce a machine, so that the instructions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, transform and control transistors, values stored in memorylocations, and other hardware components within such circuitry toimplement the functions/acts specified in the block diagrams and/orflowchart block or blocks, and thereby create means (functionality)and/or structure for implementing the functions/acts specified in theblock diagrams and/or flowchart block(s). Additionally, the computerprogram instructions may also be stored in a tangible computer-readablemedium that can direct a computer or other programmable data processingapparatus to function in a particular manner, such that the instructionsstored in the computer-readable medium produce an article of manufactureincluding instructions which implement the functions/acts specified inthe block diagrams and/or flowchart block or blocks.

As alluded to previously, tangible, non-transitory computer-readablemedium may include an electronic, magnetic, optical, electromagnetic, orsemiconductor data storage system, apparatus, or device. More specificexamples of the computer-readable medium would include the following: aportable computer diskette, a random access memory (RAM) circuit, aread-only memory (ROM) circuit, an erasable programmable read-onlymemory (EPROM or Flash memory) circuit, a portable compact discread-only memory (CD-ROM), and a portable digital video disc read-onlymemory (DVD/Blu-ray). The computer program instructions may also beloaded onto or otherwise downloaded to a computer and/or otherprogrammable data processing apparatus to cause a series of operationalsteps to be performed on the computer and/or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions/acts specified inthe block diagrams and/or flowchart block or blocks. Accordingly,embodiments of the present invention may be embodied in hardware and/orin software (including firmware, resident software, micro-code, etc.)that runs on a processor such as a digital signal processor, which maycollectively be referred to as “circuitry,” “a module” or variantsthereof.

Further, in at least some additional or alternative implementations, thefunctions/acts described in the blocks may occur out of the order shownin the flowcharts. For example, two blocks shown in succession may infact be executed substantially concurrently or the blocks may sometimesbe executed in the reverse order, depending upon the functionality/actsinvolved. Moreover, the functionality of a given block of the flowchartsand/or block diagrams may be separated into multiple blocks and/or thefunctionality of two or more blocks of the flowcharts and/or blockdiagrams may be at least partially integrated. Moreover, the acts,steps, functions, components or blocks illustrated in a particularflowchart may be inter-mixed or otherwise inter-arranged with the acts,steps, functions, components or blocks illustrated in another flowchartin order to effectuate additional variations, modifications andconfigurations with respect to one or more implementations for purposesof the present patent disclosure. Moreover, other blocks may beadded/inserted between the blocks that are illustrated. Finally,although some of the diagrams include arrows on communication paths toshow a primary direction of communication, it is to be understood thatcommunication may occur in the opposite direction relative to thedepicted arrows.

Although various embodiments have been shown and described in detail,the claims are not limited to any particular embodiment or example. Noneof the above Detailed Description should be read as implying that anyparticular component, element, step, act, or function is essential suchthat it must be included in the scope of the claims. Reference to anelement in the singular is not intended to mean “one and only one”unless explicitly so stated, but rather “one or more.” All structuraland functional equivalents to the elements of the above-describedembodiments that are known to those of ordinary skill in the art areexpressly incorporated herein by reference and are intended to beencompassed by the present claims. Accordingly, those skilled in the artwill recognize that the exemplary embodiments described herein can bepracticed with various modifications and alterations within the spiritand scope of the claims appended below.

What is claimed is:
 1. A radio dot (RD) element operable in an accesssystem for providing access with respect to information in InternetProtocol (IP) version 6 (IPv6) over Low Power Wireless Personal AreaNetwork (6LoWPAN) format, the RD element comprising: a cable front-end(FE) block for interfacing with an Ethernet cable link connecting to aRadio Unit (RU) element disposed in the access system; a radio FE blockcoupled to the cable FE block and an antenna operative to receive andtransmit radio signals for effectuating radio communications withrespect to one or more user equipment (UE) devices; a sensor componentconfigured to generate sensor data with respect to a measurementvariable; a processor coupled to the sensor component and a modeminterfacing with the cable FE block, the processor configured tofacilitate packaging of the sensor data as 6LoWPAN data (“6LO data”)packets; and a control channel repackager operative under control of theprocessor for repackaging the 6LO data packets to be transmitted via themodem as a control channel message in a format specified for a controlchannel associated with the Ethernet cable link between the RU elementand the RD element.
 2. The RD element as recited in claim 1, wherein thesensor component comprises at least one or more of temperature sensors,moisture sensors, light sensors, pressure sensors, motion sensors,biological sensors, chemical sensors, and/or environmental qualitysensors.
 3. The RD element as recited in claim 1, wherein the cable FEblock is operative to receive signals from the RU element relative tothe wireless communications in a downlink frequency band of a frequencyband plan associated with the Ethernet cable link.
 4. The RD element asrecited in claim 1, wherein the cable FE block is operative to transmitsignals to the RU element relative to the wireless communications in anuplink frequency band of a frequency band plan associated with theEthernet cable link.
 5. The RD element as recited in claim 1, whereinthe radio communications comprise at least one of 3rd GenerationPartnership Project (3GPP)-compliant cellular radio communications andIEEE 802.11 communications.
 6. A radio dot (RD) element operable in anaccess system for providing access with respect to information inInternet Protocol (IP) version 6 (IPv6) over Low Power Wireless PersonalArea Network (6LoWPAN) format, the RD element comprising: a cablefront-end (FE) block for interfacing with an Ethernet cable linkconnecting to a Radio Unit (RU) element disposed in the access system; aradio FE block coupled to the cable FE block and an antenna operative toreceive and transmit radio signals for effectuating radio communicationswith respect to one or more user equipment (UE) devices; a sensorcomponent including a protocol stack configured to generate sensor datawith respect to a measurement variable as 6LoWPAN data (“6LO data”)packets; a processor coupled to the sensor component and a modeminterfacing with the cable FE block; and a control channel repackageroperative under control of the processor for repackaging the 6LO datapackets to be transmitted via the modem as a control channel message ina format specified for a control channel associated with the Ethernetcable link between the RU element and the RD element.
 7. The RD elementas recited in claim 6, wherein the sensor component comprises at leastone or more of temperature sensors, moisture sensors, light sensors,pressure sensors, motion sensors, biological sensors, chemical sensors,and/or environmental quality sensors.
 8. The RD element as recited inclaim 6, wherein the cable FE block is operative to receive signals fromthe RU element relative to the radio communications in a downlinkfrequency band of a frequency band plan associated with the Ethernetcable link.
 9. The RD element as recited in claim 6, wherein the cableFE block is operative to transmit signals to the RU element relative tothe radio communications in an uplink frequency band of a frequency bandplan associated with the Ethernet cable link.
 10. The RD element asrecited in claim 6, wherein the radio communications comprise at leastone of 3rd Generation Partnership Project (3GPP)-compliant cellularradio communications and IEEE 802.11 communications.
 11. A radio dot(RD) element operable in an access system for providing access withrespect to information in Internet Protocol (IP) version 6 (IPv6) overLow Power Wireless Personal Area Network (6LoWPAN) format, the RDelement comprising: a cable front-end (FE) block for interfacing with anEthernet cable link connecting to a Radio Unit (RU) element disposed inthe access system; a radio FE block coupled to the cable FE block and anantenna operative to receive and transmit radio signals for effectuatingradio communications with respect to one or more user equipment (UE)devices; an access point (AP) configured to facilitate transmission andreception of 6LoWPAN data (“6LO data”) packets with respect to one ormore 6LoWPAN-compliant devices; a processor coupled to the AP and amodem interfacing with the cable FE block; and a control channelrepackager operative under control of the processor for repackaging the6LO data packets received via the AP to be transmitted via the modem asa control channel message in a format specified for a control channelassociated with the Ethernet cable link between the RU element and theRD element.
 12. The RD element as recited in claim 11, wherein theantenna of the radio FE block is shared by the AP.
 13. The RD element asrecited in claim 12, further comprising a filter operative to separatethe radio signals for effectuating radio communications with the UEdevices from radio signals for effectuating the transmission andreception of 6LO data packets with respect to the 6LoWPAN-compliantdevices.
 14. The RD element as recited in claim 11, wherein the AP iscoupled to a separate antenna operative to effectuate the transmissionand reception of 6LO data packets with respect to the 6LoWPAN-compliantdevices.
 15. The RD element as recited in claim 11, wherein the cable FEblock is operative to receive signals from the RU element relative tothe radio communications in a downlink frequency band of a frequencyband plan associated with the Ethernet cable link.
 16. The RD element asrecited in claim 11, wherein the cable FE block is operative to transmitsignals to the RU element relative to the radio communications in anuplink frequency band of a frequency band plan associated with theEthernet cable link.
 17. The RD element as recited in claim 11, whereinthe radio communications comprise at least one of 3rd GenerationPartnership Project (3GPP)-compliant cellular radio communications andIEEE 802.11 communications.
 18. A method operating at a radio dot (RD)element disposed in an access system for providing access with respectto information in Internet Protocol (IP) version 6 (IPv6) over Low PowerWireless Personal Area Network (6LoWPAN) format, the method comprising:obtaining source data; determining if the source data is compliant withthe 6LoWPAN format; and if so, repackaging the 6LoWPAN-compliant sourcedata to be transmitted as a control channel message in a formatspecified for a control channel associated with an Ethernet cable linkbetween the RD element and a Radio Unit (RU) element coupled thereto anddisposed in the access system.
 19. The method as recited in claim 18,further comprising: upon determining that the source data is not6LoWPAN-compliant, effectuating packaging of the non-compliant sourcedata as 6LoWPAN data (“6LO data”) packets; and repackaging the 6LO datapackets to be transmitted as the control channel message in a formatspecified for a control channel associated with the Ethernet cable linkbetween the RD and RU elements.
 20. The method as recited in claim 18,further comprising: upon determining that the source data is not6LoWPAN-compliant, repackaging the non-compliant source data to betransmitted as the control channel message in a format specified for acontrol channel associated with the Ethernet cable link between the RDand RU elements.
 21. The method as recited in claim 18, wherein thesource data is obtained from a sensor component comprising at least oneor more of temperature sensors, moisture sensors, light sensors,pressure sensors, motion sensors, biological sensors, chemical sensors,and/or environmental quality sensors.
 22. The method as recited in claim18, wherein the source data is obtained via a 6LoWPAN access point (AP)configured to facilitate transmission and reception of 6LoWPAN datapackets with respect to one or more 6LoWPAN-compliant devices.
 23. Anon-transitory computer-readable medium containing instructions storedthereon which, when executed by a processor of a radio dot (RD) elementconfigured to operate in an access system, facilitate access withrespect to information in Internet Protocol (IP) version 6 (IPv6) overLow Power Wireless Personal Area Network (6LoWPAN) format, thecomputer-readable medium comprising: a code portion for obtaining andprocessing source data; a code portion for determining if the sourcedata is compliant with the 6LoWPAN format; and a code portion,responsive to determining that the source data is compliant with the6LoWPAN format, for repackaging the 6LoWPAN-compliant source data to betransmitted as a control channel message in a format specified for acontrol channel associated with an Ethernet cable link between the RDelement and a Radio Unit (RU) element coupled thereto and disposed inthe access system.
 24. The non-transitory computer-readable medium asrecited in claim 23, further comprising: a code portion, responsive todetermining that the source data is not 6LoWPAN-compliant, foreffectuating packaging of the non-compliant source data as 6LoWPAN data(“6LO data”) packets; and a code portion for repackaging the 6LO datapackets to be transmitted as the control channel message in a formatspecified for a control channel associated with an Ethernet cable linkbetween the RD and RU elements.
 25. The non-transitory computer-readablemedium as recited in claim 23, further comprising: a code portion,responsive to determining that the source data is not 6LoWPAN-compliant,for repackaging non-compliant source data to be transmitted as thecontrol channel message in a format specified for a control channelassociated with an Ethernet cable link between the RD and RU elements.26. The non-transitory computer-readable medium as recited in claim 23,wherein the source data is obtained from a sensor component comprisingat least one or more of temperature sensors, moisture sensors, lightsensors, pressure sensors, motion sensors, biological sensors, chemicalsensors, and/or environmental quality sensors.
 27. The non-transitorycomputer-readable medium as recited in claim 23, wherein the source datais obtained via a 6LoWPAN access point (AP) configured to facilitatetransmission and reception of 6LoWPAN data (“6LO data”) packets withrespect to one or more 6LoWPAN-compliant devices.